Skip to content

Conversation

@forsyth2
Copy link
Collaborator

Bump to 1.5.0rc4

@forsyth2 forsyth2 self-assigned this Oct 28, 2025
@forsyth2 forsyth2 added the Update version Code specifically to update the version label Oct 28, 2025
@forsyth2 forsyth2 merged commit e7a1e22 into main Oct 28, 2025
5 checks passed
@forsyth2 forsyth2 deleted the v1.5.0rc4 branch October 28, 2025 21:57
@forsyth2
Copy link
Collaborator Author

zstash rc4

Release process notes:

Step 1: testing

On Chrysalis:

cd ~/ez/zstash
git status
# branch update-authentications
# nothing to commit
git fetch upstream
git checkout main
git reset --hard upstream/main
git log
# Last commit: Update auth tests (#397)
# Good, matches https://github.com/E3SM-Project/zstash/commits/main/
# Good, hashes match
lcrc_conda # Activate conda
conda clean --all --y
conda env create -f conda/dev.yml -n zstash_dev_20251028
conda activate zstash_dev_20251028
python -m pip install .
pytest tests/unit/test_*.py
# 1 passed in 2.20s
python -m unittest tests/integration/python_tests/group_by_command/test_*.py
# Ran 69 tests in 56.460s
# OK (skipped=32)
python -m unittest tests/integration/python_tests/group_by_workflow/test_*.py
# Ran 4 tests in 6.286s
# OK

We did more extensive testing as part of #397.

Step 2: Bump versions

Step 2a: Confluence

Update https://e3sm.atlassian.net/wiki/spaces/DOC/pages/129732419/Packages+in+the+E3SM+Unified+conda+environment:

  • E3SM Unified 1.11.0: zstash v1.4.4
  • E3SM Unified 1.11.1: zstash v1.4.4
  • E3SM Unified 1.12.0: zstash v1.5.0 (We updated this when we made rc1)

Step 2b: zstash repo

git fetch upstream main
git checkout -b v1.5.0rc4 upstream/main
tbump 1.5.0rc4 --no-tag
# Last commit: Bump to 1.5.0rc4
# Creates commit, but doesn't push it (because branch isn't named `main`)
git push upstream v1.5.0rc4
# Follow example of https://github.com/E3SM-Project/zstash/pull/392, https://github.com/E3SM-Project/zstash/pull/394
# Create, add "Update version" label" to, and merge https://github.com/E3SM-Project/zstash/pull/399

git fetch upstream
git checkout main
git reset --hard upstream/main
git tag -a v1.5.0rc4 -m "v1.5.0rc4"
git branch -D v1.5.0rc4
git push upstream v1.5.0rc4

v1.5.0rc4 now appears on Tags but not on Releases. Good, this is expected.

Step 2c: zstash-feedstock repo

On Perlmutter:

cd /global/homes/f/forsyth/zstash-feedstock
curl -sL https://github.com/E3SM-Project/zstash/archive/v1.5.0rc4.tar.gz | openssl sha256
# (stdin)= fc2d28d6623e400e2c81ffdae296a559ba0c008f66692fcbfb34f653bac40c41
nersc_conda # Activate conda
# SHA2-256(stdin)= fc2d28d6623e400e2c81ffdae296a559ba0c008f66692fcbfb34f653bac40c41
git status
# Check for uncommitted changes
git fetch upstream dev
git checkout -b v1.5.0rc4 upstream/dev
emacs recipe/meta.yaml
# In `recipe/meta.yaml`, update the version and sha256 (and the build number if needed):
# {% set version = "1.5.0rc4" %}
# sha256: ... # The sha256 from the previous step
# number: 0 # build >>> number should always be 0

# Do we need to edit any dependencies?
# Visit https://github.com/E3SM-Project/zstash/compare/v1.5.0rc3...v1.5.0rc4
# There are no changes to conda/ or /.github directories, or any dependency changes
# So we don't need to change anything here

git add -A
git commit -m "v1.5.0rc4"
git push forsyth2 v1.5.0rc4
# Follow example of https://github.com/conda-forge/zstash-feedstock/pull/17, https://github.com/conda-forge/zstash-feedstock/pull/18

Created conda-forge/zstash-feedstock#21

New in this rc

For reference, this adds the following PRs on top of rc3:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Update version Code specifically to update the version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants